Method of adjusting bluetooth connectivity for expediting access controls

ABSTRACT

A method of controlling access through a Bluetooth connection is provided. The method comprising: detecting Bluetooth advertisements of one or more access controllers using a mobile device application; determining whether to connect to the Bluetooth advertisements using the mobile device application; connecting the mobile device application to each of the one or more access controllers using separate Bluetooth connections; enumerating services of each access controller using the mobile device application; authenticating the mobile device application by transferring a credential; detecting intent of the mobile device application to engage a specific access controller; and activating a lock actuator within the specific access controller.

BACKGROUND

The subject matter disclosed herein generally relates to the field ofaccess control systems, and more particularly to an apparatus and methodfor establishing access controls through Bluetooth connections.

Existing access controls may allow a person to activate an accesscontroller to unlock a lock through a Bluetooth capable mobile device.However Bluetooth connectivity is often cumbersome and slow, thus a moreefficient solution is desired.

BRIEF SUMMARY

According to one embodiment, a method of controlling access through aBluetooth connection is provided. The method comprising: detectingBluetooth advertisements of one or more access controllers using amobile device application; determining whether to connect to theBluetooth advertisements using the mobile device application; connectingthe mobile device application to each of the one or more accesscontrollers using separate Bluetooth connections; enumerating servicesof each access controller using the mobile device application;authenticating the mobile device application by transferring acredential; detecting intent of the mobile device application to engagea specific access controller; and activating a lock actuator within thespecific access controller.

In addition to one or more of the features described above, or as analternative, further embodiments may include: disconnecting the mobiledevice application from each access controller where intent was notdetected.

In addition to one or more of the features described above, or as analternative, further embodiments may include: maintaining the Bluetoothconnection between the mobile device application and each of the accesscontrollers for a selected period of time after authenticating themobile device application and before detecting intent.

In addition to one or more of the features described above, or as analternative, further embodiments may include where intent is detectedwhen the mobile device application is within a selected range of thespecific access controller.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the one or moreaccess controllers are each operably connected to a turnstile.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the one or moreaccess controllers are each operably connected to a door.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the mobile deviceapplication connects to a Bluetooth bridge, wherein the Bluetooth bridgeperforms the operations of: authenticating the mobile device applicationby transferring a credential; and detecting intent of the mobile deviceapplication to engage a specific access controller.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the intent of themobile device application to engage a specific access controller isdetected after the mobile device application is authenticated.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the intent of themobile device application to engage a specific access controller isdetected before the mobile device application is authenticated.

According to another embodiment, an access control system is provided.The access control system comprising: one or more access controllers,wherein each of the one or more access controllers transmits a Bluetoothadvertisement; a mobile device application configured to detect theBluetooth advertisements from each access controller, determine whetherto connect to the Bluetooth advertisements, and connect to each accesscontroller through separate Bluetooth connections; wherein the mobiledevice application is configured to enumerate services of each accesscontroller after connecting to each access controller; wherein eachaccess controller authenticates the mobile device application; wherein alock actuator is configured to actuate when an intent of the mobiledevice application to engage a specific access controller containing thelock actuator is detected.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the mobile deviceapplication disconnects from each access controller where intent is notdetected after intent is detected to engage the specific accesscontroller.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the mobile deviceapplication maintains the Bluetooth connection between the mobile deviceapplication and each of the access controllers for a selected period oftime after the mobile device application is authenticated and beforeintent is detected.

In addition to one or more of the features described above, or as analternative, further embodiments may include where intent is detectedwhen the mobile device application is within a selected range of thespecific access controller.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the one or moreaccess controllers are each operably connected to a turnstile.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the one or moreaccess controllers are each operably connected to a door.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the mobile deviceapplication connects to each of the one or more access controllersthrough a Bluetooth bridge, the Bluetooth bridge being configured toauthenticate the mobile device application for the access controllersand detect the intent of the mobile device application to engage aspecific access controller.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the intent of themobile device application to engage a specific access controller isdetected after the mobile device application is authenticated.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the intent of themobile device application to engage a specific access controller isdetected before the mobile device application is authenticated.

According to another embodiment, a method of controlling access througha Bluetooth connection is provided. The method comprising: detectingBluetooth advertisements of one or more access mobile deviceapplications using an access controller; determining whether to connectto the Bluetooth advertisements using the access controller; connectingthe access controller to each of the one or more mobile deviceapplications using separate Bluetooth connections; enumerating servicesof each mobile device application using the access controller;authenticating each mobile device application by transferring acredential; detecting intent of a specific mobile device application toengage the access controller; and activating a lock actuator within theaccess controller.

In addition to one or more of the features described above, or as analternative, further embodiments may include: disconnecting the accesscontroller from each mobile device application where intent was notdetected.

In addition to one or more of the features described above, or as analternative, further embodiments may include: maintaining the Bluetoothconnection between the access controller and each of the mobile deviceapplication for a selected period of time after authenticating themobile device application and before detecting intent.

In addition to one or more of the features described above, or as analternative, further embodiments may include where intent is detectedwhen the specific mobile device application is within a selected rangeof the access controller.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the access controlleris operably connected to a turnstile.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the access controlleris operably connected to a door.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the Bluetooth bridgeconnects to one or more mobile device applications, wherein theBluetooth bridge performs the operations of: authenticating each mobiledevice application by transferring a credential; and detecting intent ofa specific mobile device application to engage the access controller.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the intent of aspecific mobile device application to engage the access controller isdetected after the one or more mobile device applications areauthenticated.

In addition to one or more of the features described above, or as analternative, further embodiments may include where the intent of aspecific mobile device application to engage the access controller isdetected before the one or more mobile device applications areauthenticated.

According to another embodiment, a computer program product tangiblyembodied on a computer readable medium is provided. The computer programproduct including instructions that, when executed by a processor, causethe processor to perform operations comprising: detecting Bluetoothadvertisements of one or more access controllers using a mobile deviceapplication; connecting the mobile device application to each of the oneor more access controllers using separate Bluetooth connections;enumerating services of each access controller using the mobile deviceapplication; authenticating the mobile device application; detectingintent of the mobile device application to engage a specific accesscontroller; and activating a lock actuator within the specific accesscontroller.

In addition to one or more of the features described above, or as analternative, further embodiments may include: disconnecting the mobiledevice application from each access controller where intent was notdetected.

Technical effects of embodiments of the present disclosure includepre-connecting a mobile device application to one or more accesscontrollers through Bluetooth before intent of a user of the mobiledevice application is known, in order to expedite the actuation processof an access controller.

The foregoing features and elements may be combined in variouscombinations without exclusivity, unless expressly indicated otherwise.These features and elements as well as the operation thereof will becomemore apparent in light of the following description and the accompanyingdrawings. It should be understood, however, that the followingdescription and drawings are intended to be illustrative and explanatoryin nature and non-limiting.

BRIEF DESCRIPTION

The following descriptions should not be considered limiting in any way.With reference to the accompanying drawings, like elements are numberedalike:

FIG. 1 illustrates a general schematic system diagram of a userauthentication system, in accordance with an embodiment of thedisclosure;

FIG. 2 illustrates a block diagram of the user authentication system, inaccordance with an embodiment of the disclosure;

FIG. 3 is a flow diagram illustrating a method of controlling through aBluetooth connection, according to an embodiment of the presentdisclosure;

FIG. 4 is a schematic of the method of FIG. 3 applied to a turnstilesystem, according to an embodiment of the present disclosure; and

FIG. 5 is a schematic of the method of FIG. 3 applied to a door system,according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

A detailed description of one or more embodiments of the disclosedapparatus and method are presented herein by way of exemplification andnot limitation with reference to the Figures.

FIG. 1 schematically illustrates an access control system 10. The system10 generally includes a mobile device 12, a server 14, and a pluralityof access controls 16, schematically illustrated as 16 a, 16 b, . . . ,16 n. It should be appreciated that, although particular systems areseparately defined in the schematic block diagrams, each or any of thesystems may be otherwise combined or separated via hardware and/orsoftware. In an embodiment, the access controls 16 may control accessthrough a turnstile. In another embodiment, the access controls 16 maycontrol access through a door.

The mobile device 12 is a wireless capable handheld device such as asmartphone that is operable to communicate with the server 14 and theaccess controls 16. The server 14 may provide credentials and other datato the mobile device 12, such as firmware or software updates to becommunicated to one or more of the access controls 16. Although theserver 14 is depicted herein as a single device, it should beappreciated that the server 14 may alternatively be embodied as amultiplicity of systems, from which the mobile device 12 receivescredentials and other data.

Each access controller 16 is a wireless-capable, restricted-access, orrestricted-use device such as wireless locks, access control readers forbuilding entry, electronic banking controls, data transfer devices, keydispenser devices, tool dispensing devices, and other restricted-usemachines. The mobile device 12 submits credentials to the accesscontrollers 16, thereby selectively permitting a user to access oractivate functions of the access controllers 16. A user may, forexample, submit a credential to an electromechanical lock to unlock it,and thereby gain access to a restricted area. In another example, a usermay submit a credential to an electronic banking control to withdrawfunds. In an alternative embodiment, the mobile device 12 may submitcredentials to the access controllers through a Bluetooth bridge 17.Advantageously, utilizing a Bluetooth bridge 17 for direct communicationwith the mobile device 12 allows for a single high-speed, high-powerdevice to be used solely for Bluetooth communication rather than autilizing separate high-speed, high power communication devices for eachaccess controller 16.

A mobile device 12 may store credentials for one or all or other of theexamples noted above, and in addition may store a plurality ofcredentials for each type of application at the same time. Somecredentials may be used for multiple access controllers 16. For example,a plurality of electronic locks in a facility may respond to the samecredential. Other credentials may be specific to a single accesscontroller 16.

With reference to FIG. 2, a block diagram of an example electronic locksystem 20 includes the access controller 16 a, the mobile device 12, andthe server 14. The access controller 16 a generally includes a lockactuator 22, a lock controller 24, a lock antenna 26, a lock transceiver28, a lock processor 30, a lock memory 32, a lock power supply 34, alock card reader 90 and a credential module 36. The access controller 16a may have essentially two readers, one reader 90 to read a physical keycard 92 and the credential module 36 to communicate with the mobiledevice 12 via the lock processor 30 and the transceiver 28 and antenna26. The access controller 16 a is responsive to credentials from themobile device 12, and may, for example, be the lock of a turnstile or adoor lock. Although the present disclosure focuses primarily oncredentials for access controller, it should be appreciated that othersystems wherein credentials are transmitted from a mobile device to anaccess controller so as to identify the user to an online system orvalidate user access rights or permissions in an offline system willbenefit herefrom. Such systems include virtual or electronic bankingsystems, machine operation systems, dispensing systems, and data accesssystems.

Upon receiving and authenticating an appropriate credential from themobile device 12 using the credential module 36, or after receiving carddata from lock card reader 90, the lock controller 24 commands the lockactuator 22 to lock or unlock a mechanical or electronic lock. The lockcontroller 24 and the lock actuator 22 may be parts of a singleelectronic or electromechanical lock unit, or may be components sold orinstalled separately.

The lock transceiver 28 is capable of transmitting and receiving data toand from at least the mobile device 12. The lock transceiver 28 may, forinstance, be a near field communication (NFC), Bluetooth, or Wi-Fitransceiver, or another appropriate wireless transceiver. The lockantenna 26 is any antenna appropriate to the lock transceiver 28. Thelock processor 30 and lock memory 32 are, respectively, data processing,and storage devices. The lock processor 30 may, for instance, be amicroprocessor that can process instructions to validate credentials anddetermine the access rights contained in the credentials or to passmessages from a transceiver to a credential module 36 and to receive aresponse indication back from the credential module 36. The lock memory32 may be RAM, EEPROM, or other storage medium where the lock processor30 can read and write data including but not limited to lockconfiguration options and the lock audit trail. The lock audit trail maybe a unified audit trail that includes events initiated by accessing thelock via the mobile device 12. The lock power supply 34 is a powersource such as line power connection, a power scavenging system, or abattery that powers the lock controller 24. In other embodiments, thelock power supply 34 may only power the lock controller 24, with thelock actuator 22 powered primarily or entirely by another source, suchas user work (e.g. turning a bolt).

While the figure shows the lock antenna 26 and the transceiver 28connected to the processor 30, this is not to limit other embodimentsthat may have additional antenna 26 and transceiver 28 connected to thecredential module 36 directly. The credential module 36 may contain atransceiver 28 and antenna 26 as part of the credential module. Or thecredential module 36 may have a transceiver 28 and antenna 26 separatelyfrom the processor 30 which also has a separate transceiver 28 andantenna 26 of the same type or different. In some embodiments, theprocessor 30 may route communication received via transceiver 28 to thecredential module 36. In other embodiments the credential module maycommunicate directly to the mobile device 12 through the transceiver 28.

The mobile device 12 generally includes a key antenna 40, a keytransceiver 42, a key processor 44, a key memory 46, a GPS receiver 48,an input device 50, an output device 52, and a key power supply 54. Thekey transceiver 42 is a transceiver of a type corresponding to the locktransceiver 28, and the key antenna 40 is a corresponding antenna. Insome embodiments, the key transceiver 42 and the key antenna 40 may alsobe used to communicate with the server 14. In other embodiments, one ormore separate transceivers and antennas may be included to communicatewith server 14. The key memory 46 is of a type to store a plurality ofcredentials locally on the mobile device 12. The mobile device 12 mayalso include a mobile device application 80. Embodiments disclosedherein, may operate through the mobile device application 80 installedon the mobile device 12.

Referring now to FIG. 3-5, while referencing components of FIGS. 1-3.FIG. 3 shows a flow chart of method 300 of controlling access through aBluetooth connection, in accordance with an embodiment of thedisclosure. Steps of the method 300 may be performed by the mobiledevice application 80 on the mobile device 12. Advantageously,significant time is saved if some of the Bluetooth connectioncommunication occurs before a user signals intent and then theconnection communication is completed after they signal intent, asillustrated by method 300. It is to be understood that the intent of auser of the mobile device 12 is transferred to the mobile deviceapplication 80 when the intent of the user is detected and thus theintent of the user becomes the intent of the mobile device application80. FIG. 4 incorporates the method 300 into a turnstile system 100 andFIG. 5 incorporates the method 300 into a door system 200. The turnstilesystem 100 generally includes one or more turnstiles 102, schematicallyillustrated as 102 a, 102 b, . . . , 102 n. In an example, the turnstilemay located in the lobby of the building to gain access to the building.The door system 200 generally includes one or more doors 202,schematically illustrated as 202 a, 202 b, . . . , 202 n. In an example,the doors may be doors to hotel rooms. At block 304, Bluetoothadvertisements of one or more access controllers 16 are detected using amobile device application 80. The access controllers 16 are continuallytransmitting their advertisements for other devices to detect andconnect. At block, 305 the mobile device application 80 may determinewhether to connect to the Bluetooth advertisements.

At block 306, the mobile device application 80 is connected using theBluetooth communication capabilities of the mobile device 12 to each ofthe one or more access controllers 16 using separate Bluetoothconnections. At block 308, the mobile device application 80 enumeratesservices of each access controller 16. Enumerating the services of eachaccess controller 16 allows the mobile device application 80 to discoverwhat operations of the access controller 16 the mobile deviceapplication 80 can control. The enumeration of services is part of theBluetooth specification. It may be required at the start of a connectionprocess so that the mobile device application 80 is aware of whatservice and characteristics of each service to use for communication.There may be different defined services and characteristics. In oneexample a standard service may be getting temperature from a thermostat,where the service would be a thermostat service and the characteristicwould be temperature. In the embodiments illustrated in FIGS. 4 and 5,the service enumerated is a credential transfer service and thecharacteristics are for reading/writing data into the credentialvalidator. This is used for transferring credential data to the accesscontroller 16 for validation to open a lock

For example, the mobile device application 80 may be able to unlock aturnstile 102 in FIG. 4 once method 300 is complete. In another example,the mobile device application 80 may be able to unlock a door 202 inFIG. 5 once method 300 is complete. At block 310, the mobile deviceapplication 80 is authenticated by transferring a credential.Authentication is where the mobile device application 80 uses theservices and characteristics to send credential data over a Bluetoothconnection to the credential module 36 for validation. This thenconfirms that the mobile device application 80 has the propercredentials . . . etc. One of skill in the art may appreciate that theremay be variations in how the authentication is done. In the example of ahotel door lock, the credential contains “card data” as a payload of thecredential. Once the credential is transferred to the access control 16it is validated by the credential module 36. Once validated, the carddata is sent into the lock controller 24 and is validated as a virtualcard read. Thus, this authentication is all done locally or offline withthe access controller 16 a (i.e. lock) making the determination. In theexample of a turnstile 102, the credential may include a ‘badge id’ thatis part of the payload of the credential. On authentication thiscredential is validated at the turnstile 102, but the badge id may besent into an access control system 10 much like a traditional badge readat a turnstile 102. In an online configuration, the access controlsystem 10 may have an access panel or other remote means that makes thedecision that this badge id is allowed into this turnstile 102 (or door202). In the online configuration, the determination to actuate theturnstile 102 would be made by the centralized access controller and/orby the access controller 16 a itself.

In one non-limiting example, the mobile device application 80 will beable to unlock a turnstile 102 in FIG. 4 once method 300 is completeonly if the credential of the mobile device application 80 has beenauthorized. In another example, the mobile device application 80 will beable to unlock a door 202 in FIG. 5 once method 300 is complete only ifthe credential of the mobile device application 80 has been authorized.In a further example of FIG. 5, a credential of a mobile deviceapplication 80 may not be authorized to unlock doors 202 of rooms thatthey are not assigned to as a guest. Advantageously, a great deal oftime is saved by establishing a connection in block 306, enumeratingservices in block 308, and authenticating the mobile device in block 310before any intent of a user of the mobile device application 80 is knownregarding which access controller 16 the mobile device application 80intends to interact with. In the example of FIG. 4, the steps ofconnecting, enumerating, and authenticating in the Bluetooth connectionprocess are all being performed as a person carrying the mobile device12 with the mobile device application 80 is approaching the turnstile102 they intent to walk through. In the example of FIG. 5, the steps ofconnecting, enumerating, and authenticating in the Bluetooth connectionprocess are all being performed as a person carrying the mobile device12 with the mobile device application 80 is walking down a hallwaytowards the door 202 they intend to enter.

At block 312, intent of a user of the mobile device application 80 toengage a specific access controller 16 a is detected. In an embodiment,the intent of the user of the mobile device application 80 to engage aspecific access controller 16 a is detected after the mobile deviceapplication 80 is authenticated. In another embodiment, the intent ofthe user of the mobile device application 80 to engage a specific accesscontroller 16 a is detected before the mobile device application 80 isauthenticated. Intent may be shown by various methods. In oneembodiment, intent may be shown by moving towards the specific accesscontroller 16 (i.e. turnstile 102 a or door 202 a) they desire to enter,which may be determined by the distances between the mobile devices 12and the access controllers 16. Distance can be inferred by the receivedsignal strength. For example, if the signal strength goes up, then themobile device 12 containing the mobile device application 80 might bemoving closer. In an embodiment, the received signal strength indicatorRSSI must cross a threshold to signal intent. In another embodiment,intent may be shown by taping the mobile device 12 containing the mobiledevice application 80 on the specific access controller 16 a or anotherreader operably connected to the specific access controller 16 a. Thetapping may be detected by an accelerometer in the mobile device 12 andalso coupled with a very high RSSI that shows which access controller 16they are tapping on. In another embodiment, intent may also be inferredbased upon past behavior, such as, for example, a mobile device 12containing the mobile device application 80 always enters the buildingthrough a specific turnstile 102 a. In yet another embodiment, intentmay be shown by a user making a selection on a screen of the mobiledevice 12 through the mobile device application 80. For example, the alist of names of one or more access controllers 16 may display on thescreen and the user may select one of the access controllers to indicatethat they want to access the turnstile 102 or door 202 linked to theaccess controller 12.

At block 314, a lock actuator 22 within the specific access controller16 a is activated, thus once intent is known the mobile deviceapplication 80 is granted access to activate the specific accesscontroller 16 a. In the example of FIG. 4, at block 314 the specificaccess controllers 16 a will unlock turnstile 102 a. In the example ofFIG. 5, at block 314 the specific access controllers 16 a will unlockdoor 202 a. In an embodiment, the lock actuator 22 may only be activatedwhen the mobile device 12 containing the mobile device application 80 isa selected distance away from the specific access controller 16 a.Distance can be determined by many different methods including but notlimited to detecting the level of received signal strength through RSSIto determine distance; an indoor locating system that may or may notutilize Bluetooth (ex: WiFi); a GPS system; and by any other means knownto one of skill in the art of determining distance from a mobile deviceto another device. Advantageously, this distance requirement may helpprevent one person at the back of a line from unlocking the turnstile102 for another person at the front of the line.

The method 300 may also include disconnecting the mobile deviceapplication 80 from each access controller 16 where intent was notdetected. For example, once it is determined where the mobile device 12containing the mobile device application 80 is heading there is noreason to maintain the Bluetooth connections to other access controllers16 that will not be used, thus freeing up Bluetooth capacity for othermobile devices. The method 300 may further include between blocks 310and 312: maintaining the Bluetooth connection between the mobile deviceapplication 80 and each of the access controllers 16 for a selectedperiod of time after authenticating the mobile device application 80 andbefore detecting intent. Advantageously, holding the Bluetoothconnection open for a selected period of time before intent isdetermined allows connecting, enumerating, and authenticating well inadvance of knowing the intent of the user of the mobile deviceapplication 80, thus speeding up the overall process and reducing thenumber of remaining steps in method 300 once intent is determined.

In an alternate embodiment, block 312 may proceed block 310. In thisalternate embodiment the steps of detection at block 304, connection atblock 306, and enumeration at block 308 would occur and then the accesscontrol system 10 would wait for intent at block 312 before doing thefull authentication at block 310. This alternate embodiment may beadvantageous if the access control 16 can only handle so manyauthenticated connections, thus then it could be easier to handle abasic connection and wait to authenticate until intent is determined.

In a second alternative embodiment, the access controllers 16 may bewired and/or wirelessly connected to a Bluetooth bridge 17, whichcontinuously projects out an advertisement for the Bluetooth bridge 17.The advertisement for the Bluetooth bridge 17 represents the wholeturnstile system 100 with all of turnstiles 102 in each lane. With theaddition of a Bluetooth bridge 17, method 300 may include sending to theBluetooth bridge 17 which turnstile 102 the mobile device 12 containingthe mobile device application 80 is at when intent is determined. Theintent would include which turnstile lane you are in (i.e. 102 a, 102 b,etc.). This determination could be made at block 312 of method 300.Determination of the lane could be done by any indoor locating means,including but not limited to: use of Bluetooth signals from each accesscontrol 16 a-16 n or other iBeacon type devices, or Wi-Fi positioning,or other well-known methods in the art of indoor positioning. Thedetermination of the lane could also be by the user selecting a laneidentifier on a screen of the mobile device 12 through the mobile deviceapplication 80, or by using a camera in the mobile device 12 to detect alane identifier, etc. Knowing which lane you are in is important for theBluetooth bridge 17 because the Bluetooth bridge 17 does not know whichturnstile 102 (or door 202) you want to go through. After the messagefrom the mobile device application 80 to the Bluetooth bridge 17 issent, the Bluetooth bridge 17 would then signal to the particularturnstile (or door 202) to open. Utilizing a Bluetooth bridge 17 isadvantageous because the Bluetooth bridge 17 can be a much higherpowered device that can handle many more connections than an embeddedconstrained system. Additionally, the Bluetooth Bridge 17 creates asingle point of connection rather than a multi-connect scenario.

In the embodiment of method 300, the mobile device application 80 is aBluetooth central and the access controls 16 are a Bluetooth peripheral.In a third alternative embodiment, the access controls 16 are theBluetooth central and the mobile device application 80 is the Bluetoothperipheral. In this third alternative embodiment, block 304 is completedin reverse and the mobile device application 80 is advertising and theaccess controllers 16 are detecting. In this third alternativeembodiment, block 306 is executed by access controllers 16 connectingautomatically to the phone. In this third alternative embodiment, atblock 308 the access controllers 16 enumerate services of the mobiledevice 308 and then read the credential from the mobile device 16 toauthenticate the mobile device application 80 at block 310. In thisthird alternative embodiment, at block 312 the mobile device application80 and/or the access controllers 12 may detect intent based upondistance/proximity/location or other means. In this third alternativeembodiment, at block 314 the access controller will activate the lockactuator 22.

While the above description has described the flow process of FIG. 3-5in a particular order, it should be appreciated that unless otherwisespecifically required in the attached claims that the ordering of thesteps may be varied.

As described above, embodiments can be in the form ofprocessor-implemented processes and devices for practicing thoseprocesses, such as a processor. Embodiments can also be in the form ofcomputer program code containing instructions embodied in tangiblemedia, such as network cloud storage, SD cards, flash drives, floppydiskettes, CD ROMs, hard drives, or any other computer-readable storagemedium, wherein, when the computer program code is loaded into andexecuted by a computer, the computer becomes a device for practicing theembodiments. Embodiments can also be in the form of computer programcode, for example, whether stored in a storage medium, loaded intoand/or executed by a computer, or transmitted over some transmissionmedium, loaded into and/or executed by a computer, or transmitted oversome transmission medium, such as over electrical wiring or cabling,through fiber optics, or via electromagnetic radiation, wherein, whenthe computer program code is loaded into an executed by a computer, thecomputer becomes an device for practicing the embodiments. Whenimplemented on a general-purpose microprocessor, the computer programcode segments configure the microprocessor to create specific logiccircuits.

The term “about” is intended to include the degree of error associatedwith measurement of the particular quantity based upon the equipmentavailable at the time of filing the application. For example, “about”can include a range of ±8% or 5%, or 2% of a given value.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the presentdisclosure. As used herein, the singular forms “a”, “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“comprises” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,element components, and/or groups thereof.

While the present disclosure has been described with reference to anexemplary embodiment or embodiments, it will be understood by thoseskilled in the art that various changes may be made and equivalents maybe substituted for elements thereof without departing from the scope ofthe present disclosure. In addition, many modifications may be made toadapt a particular situation or material to the teachings of the presentdisclosure without departing from the essential scope thereof.Therefore, it is intended that the present disclosure not be limited tothe particular embodiment disclosed as the best mode contemplated forcarrying out this present disclosure, but that the present disclosurewill include all embodiments falling within the scope of the claims.

What is claimed is:
 1. A method of controlling access through aBluetooth connection, the method comprising: detecting Bluetoothadvertisements of one or more access controllers using a mobile deviceapplication; determining whether to connect to the Bluetoothadvertisements using the mobile device application; connecting themobile device application to each of the one or more access controllersusing separate Bluetooth connections; enumerating services of eachaccess controller using the mobile device application; authenticatingthe mobile device application by transferring a credential; detectingintent of the mobile device application to engage a specific accesscontroller; and activating a lock actuator within the specific accesscontroller.
 2. The method of claim 1, further comprising: disconnectingthe mobile device application from each access controller where intentwas not detected.
 3. The method of claim 1, further comprising:maintaining the Bluetooth connection between the mobile deviceapplication and each of the access controllers for a selected period oftime after authenticating the mobile device application and beforedetecting intent.
 4. The method of claim 1, wherein: intent is detectedwhen the mobile device application is within a selected range of thespecific access controller.
 5. The method of claim 1, wherein: the oneor more access controllers are each operably connected to a turnstile.6. The method of claim 1, wherein: the one or more access controllersare each operably connected to a door.
 7. The method of claim 1,wherein: the mobile device application connects to a Bluetooth bridge,wherein the Bluetooth bridge performs the operations of: authenticatingthe mobile device application by transferring a credential; anddetecting intent of the mobile device application to engage a specificaccess controller.
 8. The method of claim 1, wherein: the intent of themobile device application to engage a specific access controller isdetected after the mobile device application is authenticated.
 9. Themethod of claim 1, wherein: the intent of the mobile device applicationto engage a specific access controller is detected before the mobiledevice application is authenticated.
 10. An access control systemcomprising: one or more access controllers, wherein each of the one ormore access controllers transmits a Bluetooth advertisement; a mobiledevice application configured to detect the Bluetooth advertisementsfrom each access controller, determine whether to connect to theBluetooth advertisements, and connect to each access controller throughseparate Bluetooth connections; wherein the mobile device application isconfigured to enumerate services of each access controller afterconnecting to each access controller; wherein each access controllerauthenticates the mobile device application; wherein a lock actuator isconfigured to actuate when an intent of the mobile device application toengage a specific access controller containing the lock actuator isdetected.
 11. The access control system of claim 10, wherein: the mobiledevice application disconnects from each access controller where intentis not detected after intent is detected to engage the specific accesscontroller.
 12. The access control system of claim 10, wherein: themobile device application maintains the Bluetooth connection between themobile device application and each of the access controllers for aselected period of time after the mobile device application isauthenticated and before intent is detected.
 13. The access controlsystem of claim 10, wherein: intent is detected when the mobile deviceapplication is within a selected range of the specific accesscontroller.
 14. The access control system of claim 10, wherein: the oneor more access controllers are each operably connected to a turnstile.15. The access control system of claim 10, wherein: the one or moreaccess controllers are each operably connected to a door.
 16. The accesscontrol system of claim 10, wherein: the mobile device applicationconnects to each of the one or more access controllers through aBluetooth bridge, the Bluetooth bridge being configured to authenticatethe mobile device application for the access controllers and detect theintent of the mobile device application to engage a specific accesscontroller.
 17. The access control system of claim 10, wherein: theintent of the mobile device application to engage a specific accesscontroller is detected after the mobile device application isauthenticated.
 18. The access control system of claim 10, wherein: theintent of the mobile device application to engage a specific accesscontroller is detected before the mobile device application isauthenticated.
 19. A method of controlling access through a Bluetoothconnection, the method comprising: detecting Bluetooth advertisements ofone or more mobile device applications using an access controller;determining whether to connect to the Bluetooth advertisements using theaccess controller; connecting the access controller to each of the oneor more mobile device applications using separate Bluetooth connections;enumerating services of each mobile device application using the accesscontroller; authenticating each mobile device application bytransferring a credential; detecting intent of a specific mobile deviceapplication to engage the access controller; and activating a lockactuator within the access controller.
 20. The method of claim 19,further comprising: disconnecting the access controller from each mobiledevice application when intent was not detected to engage the accesscontroller.
 21. (canceled)
 22. (canceled)
 23. (canceled)
 24. (canceled)25. (canceled)
 26. (canceled)
 27. (canceled)
 28. (canceled) 29.(canceled)